Search Results

This SAE Recommended Practice is applicable to all light duty and medium duty passenger vehicles and trucks with feedback fuel control system. Specific applications of this document include diagnostic, service and repair manuals, repair data bases, and off-board readout devices. This document focuses on a diagnostic code format and code messages for automotive electronic control systems. The use and appropriate updating of this document is strongly encouraged; however, this document does not prohibit the use of additional codes for additional diagnostics.

This SAE Recommended Practice defines the requirements of OBD II Scan Tools, i.e. test equipment that will interface with vehicle modules in support of the OBD II diagnostic requirements. It covers the required capabilities of and conformance criteria for OBD II Scan Tools.

This SAE Recommended Practice defines diagnostic test modes, and request and response messages, necessary to be supported by vehicle manufacturers and test tools to meet the requirements of the California OBD II regulations, which pertain to vehicle emission-related data only. These messages are intended to be used by any service tool capable of performing California OBD II mandated diagnostics. Diagnostic Test Modes included in this document are: For each test mode, this document includes: a Functional descriptions of test mode b Request and response message formats

This SAE Recommended Practice establishes a uniform practice for protecting vehicle modules from "unauthorized" intrusion through a vehicle diagnostic data communication link. The security system represents a recommendation for motor vehicle manufacturers and provides flexibility for them to tailor their system to their specific needs. The vehicle modules addressed are those that are capable of having solid-state memory contents altered external to the electronic module through a diagnostic data communication link. Improper memory content alteration could potentially damage the electronics or other vehicle modules; risk the vehicle compliance to government legislated requirements; or risk the vehicle manufacturer's security interests. This document is intended to meet the "tampering protection" provisions of California Air Resources Board OBD II regulations and does not imply that other security measures are not required nor possible.

The utilities defined for J2037 are designed to facilitate manufacturing and service diagnosis requirements. Definition of the capability includes definition of standard messages and the dialogue necessary to provide the capability. The standard messages will be distinguished by the contents of the first data byte which specifies the diagnostic operation. Note that some vehicle applications will not require the implementation of all the defined diagnostic capabilities, and consequently, these applications will not support all message modes.